Allow remote components on NAS compute nodes; check for either k or NAS in examples - #245
Merged
Merged
Conversation
…ts can be run within NAS compute nodes
kejacobson
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remote components on a NAS compute node currently don't work due to inability to communicate between compute nodes. This change sets up the ssh port forwarding to jump through the front-end node the job was launched from, $PBS_O_HOST.
Also: supersonic panel examples now automatically check if the K or NAS HPC is being used so that that doesn't need to be manually changed. The user will still need to enter their own group_list if using NAS.